Java migration guide: Spring Boot 4 test code changes - #2734
Merged
Conversation
rjayasinghe
requested review from
danjoa,
renejeglinsky and
smahati
as code owners
July 9, 2026 08:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new subsection Test Code Changes under the existing Spring Boot 4 section in the CAP Java 4 → 5 migration guide (
java/migration.md).CAP Java 5 mandates Spring Boot 4. Normal application code is rarely affected because it doesn't touch Spring Boot's APIs directly, but test code typically does — Spring Boot 4's new module structure causes package name changes that can break existing test classes (e.g. the test slice annotations like
@AutoConfigureMockMvc,@WebMvcTest,@DataJpaTest).The new subsection: